Almathera Ten Pack 3: CDPD 3/Almathera Ten on Ten - Disc 3: CDPD3.iso/jam/jamdisk4/arpuserdocs3.1/ares

Text File | 1995-03-18 | 5KB | 133 lines

     ARes(V1.3)              ARP User's Manual              ARes(V1.3)



     NAME
          ARes - Add, view or remove resident programs.

     SYNOPSIS
          ARes Filename/..., AS/k REMOVE/s FULL/s FORCE/s NOCHECK/s

     DESCRIPTION
          ARes is ARP's alternative to the Commodore Resident.  This
          command should be used instead of Resident when using the
          Arp Shell (ASH) or any other shell which uses the
          arp.library process functions. This resident facility
          supports a "Load on demand" feature, which will only bring
          the program into memory when it is actually accessed.  If it
          is not accessed, it will never be loaded.  Not only does
          this save memory in the case of not using a program, but it
          dramatically speeds up startup scripts which make a lot of
          programs resident.

          The ARP Resident allows a program to set its own stack
          size, which prevents crashes and also typically saves
          you memory (all the ARP programs, when run from a shell
          which uses the arp.library process functions, will use
          only a 4000 byte stack).  The ARP resident facility also
          checks to make sure a program is safe to run as resident,
          and will refuse to do so if it is not.  This means you do
          not have to crash your computer to determine which programs
          may be safely run as resident.

          ARes by itself displays a list of all currently resident
          programs and statistics on their usage. To add a program to
      the list, simply supply its name.  Like most ARP commands,
      ARes will accept an unlimited number of filenames with each
      invocation.  If you supply a complete pathname, the resident
      facility will use that name to match on AND will also match
      on the filename.  This allows you (for example) to make
      Fault resident as C:Fault, and access it as both Fault and
      C:Fault.  This allows shells to give fast error reporting.

     OPTIONS
          AS   Ordinarily, a command is stored on the resident list
               with the same name as you supply on the command line.
               To change this, you use the AS keyword.  For example,
               "ARes DF0:c/DIR as Dir" will use the name "Dir" on the
               list, instead of "DF0:c/Dir".

          REMOVE
               Removes a resident program from the list.  If a command
               is stored with its full pathname, you do not need to
               type the whole name, only the filename it is stored
               under to remove it.  For example, to remove a file
               whose resident name is "DF0:c/Dir" you need only type
               "ARes REMOVE Dir".



     Page 1                                          (printed 4/28/89)






     ARes(V1.3)              ARP User's Manual              ARes(V1.3)



          FULL This keyword gives a more informative display than the
               default.

          FORCE
               This keyword will force the command or commands into
               memory immediately, overriding the load on demand
               feature.

          NOCHECK
               This keyword disables checksum validation on the
               resident program before running it. Every program is
           normally checksumed before each execution and if the
           checksum fails, the resident version of the program is
           not run. There are some applications available that may
           fail a checksum, but can still be run safely from the
           resident list if only one copy of the program is run
           at a time.  The NOCHECK keyword will allow you to run
           these applications and will insure that only one copy
           is run from the resident list. Indiscriminate use of
           this option is likely to cause a system crash by trying
           to run programs that cannot be run from the resident
           list.

     Possible Problems
          Not all programs will be happy as resident, it is probably
          fair to say that the large majority of commercial and public
          domain software will not be usable as resident.  All the ARP
          programs, and some commercial software such as TxED+ V2.02
          will work beautifully as Resident.  Hopefully more software
          developers will take advantage of the Resident code features
          of ARP, since it provides a very memory efficient way to run
      multiple copies of programs, as well as faster program loads.

          In general, if a program does not work as Resident, the
          resident manager will be able to detect it before running
          your program, and will put up a requester informing you of
          this fact.  You can simply remember not to make that
          particular program resident in the future.  Even if a
          program returns a checksum error, you can remove it using
          the REMOVE switch to recover the memory.

     EXAMPLE
          ARes C:Type    ; make type resident
          Run Type DOCUMENTS To PRT:
          Run C:Type DOCUMENTS TO SER:
          DF0:C/Type DOCUMENTS

          Note that the last example will not use the resident program
          list, but the disk based version instead.  The first two
          examples will access the resident program.

     SEE ALSO
          AshManual Run ARun


     Page 2                                          (printed 4/28/89)